home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Libris Britannia 4
/
science library(b).zip
/
science library(b)
/
COMMUNIC
/
BULLETIN
/
0340A.ZIP
/
MITES!.ARC
/
MITES.DOC
Wrap
Text File
|
1987-01-24
|
9KB
|
198 lines
Reported 'Mite' List for Opus
January 18,1987
The following is a list of reported mites in the 0.0 version of Opus.
None of the reported problems have been tested or verified by the author. I
just note 'em and go to the next one. If you can DISPROVE any of the below,
please send a note to me at 124/210, one of the INFO nodes, or post it in the
Meadow.
--- Jon
1. The highest message pointer is not updated when you reply to a message.
The only way to view this message is to exit the area and return.
2. GBS files do not necessarily count lines properly. This means that more
prompts may not be displayed in the right places.
3. In the Event Manager, Deleted and Disabled are reversed.
4. It appears that the file CKermit.Log is hard-coded. You should keep a
directory called 'C:\Opus' until all the hard coded routines are
eliminated.
5. The use of O)utside from either the main menu or the sysop menu
reportedly flags the user's record for deletion. Any information on
this would be greatly appreciated.
6. The sample control file does not include the line to display the ByeBye
file. You should add a line 'Uses ByeBye C:\Opus\MSC\ByeBye' (or
whatever).
7. Some users have reported problems with embedded commands and ANSI. If
you are experiencing this, try changing the order of the embedded
commands and/or putting them on a separate line which does not include
ANSI sequences.
8. Area 0 does not show in an area list as it did in Fido<tm>. It will be
S)canned, but will not show in the areas listing.
9. The sysop's name does not display in a U)ser list.
10. Opus only creates the file LastUser.Bbs if the user accesses outside
commands.
11. If a user name contains the character '|', Opus treats it as a carriage
return and considers the characters after it as the entry for the next
prompt. This should only be a problem in Northern Europe where this
character is used for a character not contained in the IBM ROM.
12. ^K is NOT a valid code to abort an operation. In this version, it was
never meant to be.
13. During a message scan, More will not display even if the user has it
enabled.
14. The external programs do not make a log entry for the transaction, they
just note that the program was called.
15. Message headers display the full width of the field, including trailing
blanks.
16. OpusNode does not properly handle long distance nodes within the same
area code as your own when using the '-s' option.
17. When returning from the Opus!Comm routines (primarily ^S and ^Q), ANSI
sequences will drop a character.
18. There are still problems with the plus and minus commands in the
message section.
19. Someone has mentioned that they cannot get personal welcome messages to
work. The format of the file should be 'x.Bbs' where x is the zero
based record number without leading zeroes. Can anybody verify this???
SCS Note: They work find if they are placed in the OPUS root area.
20. There have been reports of the daylimit file not being displayed. Once
again, can this be verified???
21. When scanning messages, Opus will scan the current area first, then
start at the lowest area and work up, including the current area.
22. The message editor does not allow you to insert a blank line as the
first line of the message.
23. The message editor does NOT convert case as Fido<tm> does. This allows
names like Van de Loo, but also will allow wYnN wAgNeR.
24. In the Matrix area, users with a privilege of SYSOP cannot read private
messages, nor can they delete messages not addressed to them.
SCS Note: Not true. This only happens if the Matix Area is not
declared properly.
25. Command stacking does not work when entering messages. This is all I
have on this one. Could someone please verify???
26. Regardless of privilege, you cannot enter a Matrix message without any
credit.
27. Opus!Comm does not check to see if it has already been installed. If
you call it multiple times, it will keep eating memory.
28. Automatic tossing of EchoMail fails if there is no space between AREA:
and the area tag. Could someone verify???
29. The area change command is an absolute boundary. This means you cannot
stack commands across the area change command.
30. In the message area, messages that have replies point to the reply, but
the reply does not point back to the original. This means that a
message that has a reply will say that it does, but if you read the
reply first, you will never be shown the original message.
31. When asked for a password, Opus says that it must be four characters or
more, but it doesn't check to see that it is at least that big.
32. Passwords cannot contain curly braces. This probably extends to all
punctuation characters.
33. The password prompt allows spaces, and then recognizes only the first
word.
34. Support for DoubleDOS works is erratic on some machines.
35. If you are using SEAdog for a front-end program, Opus does not properly
interpret the parameter passed with '*t' (time till next event). This
is a result of the time handling routines provided with Lattice C. For
instance, using these routines, the date will be one off in a leap year
for the first two months of the year due to the method Lattice uses in
calculating Julian dates.
36. The lastuser file may, or may not properly show the correct baud rate.
37. Someone reported that Opus reported an error in line 12340, but I think
the Basic language version was only for evaluation purposes.
SCS Note: This is NOT an OPUS bug.
38. If you do not schedule at least one event in Opus, Opus will not limit
the caller's time in any way,shape, or form.
39. Opus does not recognize events as being anything but every day YET. If
you have events scheduled for a single day, you cannot change the day,
and Opus will treat the event as being an every day event.
40. The Yell bell will not always sound the same tones. If set to a low
value, it will be of irregular duration.
41. There are timing problems at logoff. If you are running on a fast
machine, you may experience some trouble at slower baud rates.
42. Opus displays path names as only seven characters in the log. If your
subdirectory name is eight characters long, Opus will only report the
first seven.
43. When running with snoop off, The yell message is displayed twice on the
same line; once for the log, and once for the local console.
44. Someone entered X:10 at the E)vent C)hange K)ind prompt, and Opus went
into an indefinite loop (There's no such thing as a perpetual loop).
Could someone elaborate on this???
45. You cannot kill a line in a files.bbs listing if it does not have a
file associated with it.
46. Occasionally, Opus will log a filename, and the caller will not get a
chance to enter the description due to time constraints, etc. In this
case, the next filename uploaded will become the first file's
description.
47. ScanMail will not recognize the NOECHO directive if the message is
entered in an area that Opus inserts the origin line. This is due to
the way ScanMail works, not Opus. ScanMail thinks any message with an
existing origin line originated on another board, and should be
forwarded.
48. Opus currently contains no means to delete a path from a system file
once the path has been entered short of deleting the file and starting
over.
49. Delete messages by age is NOT implemented, nor will it be due to the
existence of external renumbering programs.
50. ^OS does not always return to the calling file. This is primarily with
GBS files. Could someone check this out???
51. ^A does not work in the newuser files. Anybody seen this???
52. Matrix Refuse Crashmail may not work. Please forward info.
That's about it for this edition. If you can show that any of these
mites are invalid, we would appreciate it. If you have experienced problems
that are NOT listed, please post a note in the Meadow. If you can further
define any of these problems, please send a netmail message to me at 124/210
or contact one of the Help Nodes.
Jon Sabol
Matrix 124/210
HARDWIRED